-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Advance Debugging #5774
Advance Debugging #5774
Conversation
225056c
to
7bae251
Compare
758c4f0
to
518fc48
Compare
624192b
to
3e25344
Compare
518fc48
to
00bc2b9
Compare
3e25344
to
9604944
Compare
add7a65
to
5413b27
Compare
94c8539
to
80c4e86
Compare
5413b27
to
a0d2d2c
Compare
@akosyakov Is it ready for review? |
@tolusha I did not have time to add test sample VS Code extension to test identity of breakpoints in the plugin host process, but the rest should be good. |
@akosyakov |
@tolusha the problem is that we are going to prohibit to hard code colors in css, only css color variables can be used which are first registered via You can change base of this PR to branch of #6722, introduce new colors and update css to use them. So this PR will be prepared for testing after theming PR is merged. Colors should be registered with ids as in VS Code, i.e. with |
I'm going to reset base branch for it as #6722 and add missing colors. |
aa77210
to
872e810
Compare
c2e5e23
to
96becef
Compare
I've fixed theming, so it should be fine to merge after the theming PR is in. @thegecko I think all comments except using the context menu to add inline breakpoints were fixed. Would it be alright to tackle management of inline breakopints via the context menu separately? Right now one can add it by putting a cursor at some position and using the command palette, the debug top-level menu or the short-cut @tolusha If you are fine with changes please don't forget to give an approve. |
@akosyakov, perhaps open an issue to add the context menu item? Happy to merge as is. |
96becef
to
15af855
Compare
Signed-off-by: Anton Kosyakov <[email protected]>
Signed-off-by: Anton Kosyakov <[email protected]>
- fix #5767 - function breakpoints support - fix #5788 - preserve breakpoints identity in the plugin host process Signed-off-by: Anton Kosyakov <[email protected]>
Signed-off-by: Anton Kosyakov <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anton Kosyakov <[email protected]>
5bbb526
to
43b344d
Compare
changes were addressed: #5774 (comment)
What it does
Pause on an exception with watch expressions:
How to test
watch expressions: add watch expressions and start debugging, they should be updated as you go
exception breakpoints:
function breakpoints:
inlined breakpoints
breakpoints identity issues in the plugin host process: TBD